|
|
|
|
|
|
|
The lessons for Week 1 got you started in object-oriented programming concepts in Visual Basic. You learned important concepts in object-oriented analysis, design, and programming, as well as class inheritance and building ActiveX components. |
|
|
|
|
|
|
|
|
The purpose of the first lesson is to give you a primer on object-oriented programming that is generally universal. You read a survey of fundamental concepts in object-oriented programming that provided the foundation for the subsequent lessons in the book. You learned that a class is a design-time template that determines the behavior of objects based on it and that Visual Basic allows you to perform OOP using the class module and the Class Builder utility. |
|
|
|
|
|
|
|
|
Day 2, Fundamental Object-Oriented Analysis, presented you with the essentials of performing object-oriented analysis. You learned how to discover important entities or abstractions in your user requirements and other sources in your domain. You also learned how to implement user requirements as use cases. Moreover, you learned that the three primary roles usually involved in the use case identification process are the requirements gatherer, the object-oriented analyst, and the architect. You saw that the requirements gatherer would typically interrogate end users, business managers (or domain experts), and project managers in order to draft both a problem statement and optionally an initial requirements model. The object-oriented analyst then carefully examines the requirements model to understand the requirements and elaborate on the requirements model, to assess the implications of each requirement, and to remove inconsistencies and requirements that have been discovered to no longer |
|
|
|
|
|